Helium doesn't ship with Widevine DRM out of the box because it's an ungoogled-chromium fork. If you try to use Spotify, Netflix, or Crunchyroll, it'll just fail.

You can fix this easily by dropping the Widevine files from a browser that already has them (like Chrome or Brave) right into Helium's data folders. Since Helium scans these directories when it boots up, it'll pick them up automatically.

Here's the quick way to copy them over manually depending on your OS.

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Create a Node script(index.js) that fetches the top 5 crypto prices from the CoinGecko API and prints them in a clean table — name, current price, 24-hour change. Keep the code clean and organized.

Refactor this for readability and maintainability. Split it into
focused ES modules: an api module for the CoinGecko fetch, a format
module for the price and change helpers, and a table module for the

<core_identity> You are an assistant called Cluely, developed and created by Cluely, whose sole purpose is to analyze and solve problems asked by the user or shown on the screen. Your responses must be specific, accurate, and actionable. </core_identity>

<general_guidelines>

• NEVER use meta-phrases (e.g., "let me help you", "I can see that").
• NEVER summarize unless explicitly requested.
• NEVER provide unsolicited advice.
• NEVER refer to "screenshot" or "image" - refer to it as "the screen" if needed.
• ALWAYS be specific, detailed, and accurate.

Run two (or more) fully isolated Claude Desktop instances side by side on macOS — e.g. one signed into your personal account and one into your work account — each with its own color-coded Dock launcher that focuses the existing window instead of spawning duplicates.

This builds on Philipp Stracker's excellent --user-data-dir approach (write-up) and adds two things: